Skip to content

refactor(cache): move the task fs story into crates/vt_fs_fingerprint - #594

Open
wan9chi wants to merge 1 commit into
claude/task-fs-seamfrom
claude/extract-filesystem-tracing-e49e4b
Open

refactor(cache): move the task fs story into crates/vt_fs_fingerprint#594
wan9chi wants to merge 1 commit into
claude/task-fs-seamfrom
claude/extract-filesystem-tracing-e49e4b

Conversation

@wan9chi

@wan9chi wan9chi commented Aug 5, 2026

Copy link
Copy Markdown
Member

Motivation

The task_fs module introduced in #601 already mirrors a standalone crate — this lifts it out of the engine wholesale (stack: 3/3), so the unsettled read-write-overlap policy has a home that is reasoned about and tested on its own, with synthetic traces instead of whole-engine runs.

Six of the seven moved files are zero-diff renames (hash.rs changes two lines: pub(super) is redundant at a crate root). The genuinely new content is the crate manifest, a 22-line lib.rs of re-exports, and the README documenting the boundary and its design rationale. The engine keeps storage, archiving, env tracking, and spawning; rayon, twox-hash, and wax leave its dependency list with the moved code.

🤖 Generated with Claude Code

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown

fspy benchmark

linux

dynamic/launch             change  -0.23%  [ -8.80% ..  +8.48%]  overhead   +63.14%
dynamic/access             change  -0.66%  [-15.52% ..  +3.05%]  overhead    +6.55%
static/launch              change  +1.19%  [ -6.54% .. +13.31%]  overhead  +171.90%
static/access              change  -0.04%  [-11.64% ..  +5.57%]  overhead  +831.57%

macos

dynamic/launch             change  -0.40%  [ -4.63% ..  +4.38%]  overhead  +231.57%
dynamic/access             change  -0.33%  [ -3.88% ..  +2.67%]  overhead    +2.66%

windows

dynamic/launch             change  -0.21%  [ -1.78% ..  +1.56%]  overhead   +28.31%
dynamic/access             change  -0.19%  [ -0.77% ..  +0.58%]  overhead    +1.19%

@wan9chi
wan9chi force-pushed the claude/extract-filesystem-tracing-e49e4b branch 3 times, most recently from 0fd6243 to f53d2d1 Compare August 7, 2026 07:23
The task_fs module already mirrors a standalone crate: lift it out of the
engine wholesale so the unsettled read-write-overlap policy has a home that is
tested with synthetic traces instead of whole-engine runs. The engine keeps
storage, archiving, env tracking, and spawning; rayon, twox-hash, and wax
leave its dependency list with the moved code.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
@wan9chi
wan9chi force-pushed the claude/extract-filesystem-tracing-e49e4b branch from f53d2d1 to ad96d42 Compare August 9, 2026 03:06
@wan9chi wan9chi changed the title refactor(cache): extract filesystem fingerprinting into vt_fs_fingerprint crate refactor(cache): move the task fs story into crates/vt_fs_fingerprint Aug 9, 2026
@wan9chi
wan9chi changed the base branch from main to claude/task-fs-seam August 9, 2026 03:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant